Lifetime mixed level non-volatile memory system

ABSTRACT

A flash controller for managing at least one MLC non-volatile memory module and at least one SLC non-volatile memory module. The flash controller is adapted to determine if a range of addresses listed by an entry and mapped to said at least one MLC non-volatile memory module fails a data integrity test. In the event of such a failure, the controller remaps said entry to an equivalent range of addresses of said at least one SLC non-volatile memory module. The flash controller is further adapted to determine which of the blocks in the MLC and SLC non-volatile memory modules are accessed most frequently and allocating those blocks that receive frequent writes to the SLC non-volatile memory module and those blocks that receive infrequent writes to the MLC non-volatile memory module.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/006,299, filed Jun. 11, 2018, entitled LIFETIME MIXED LEVELNON-VOLATILE MEMORY SYSTEM, which is a continuation of U.S. patentapplication Ser. No. 14/950,553, filed Nov. 24, 2015, entitled LIFETIMEMIXED LEVEL NON-VOLATILE MEMORY SYSTEM, which a continuation of U.S.patent application Ser. No. 14/525,411, filed Oct. 28, 2014, entitledLIFETIME MIXED LEVEL NON-VOLATILE MEMORY SYSTEM, which is a divisionalof U.S. patent application Ser. No. 13/455,267, filed Apr. 25, 2012,LIFETIME MIXED LEVEL NON-VOLATILE MEMORY SYSTEM, which claims thebenefit of U.S. Provisional Application No. 61/509,257, filed Jul. 19,2011, entitled LIFETIME MIXED LEVEL NAND FLASH SYSTEM, the disclosuresof which are hereby incorporated by reference in their entirety.

This application is also related to U.S. patent application Ser. No.12/256,362, filed Oct. 22, 2008, entitled NONVOLATILE MEMORY SYSTEMSWITH EMBEDDED FAST READ AND WRITE MEMORIES, and U.S. patent applicationSer. No. 12/915,177, filed Oct. 29, 2010, entitled NONVOLATILE MEMORYSYSTEMS WITH EMBEDDED FAST READ AND WRITE MEMORIES, the disclosures ofwhich are hereby incorporated by reference in their entirety.

TECHNICAL FIELD

This application relates to a system and method for providing reliablestorage through the use of non-volatile memories and, more particularly,to a system and method of increasing the reliability and lifetime of aNAND flash storage system, module, or chip through the use of acombination of single-level cell (SLC) and multi-level cell (MLC) NANDflash storage without substantially raising the cost of the NAND flashstorage system. The memory in a total non-volatile memory system maycontain some SRAM (static random-access memory), DRAM (dynamic RAM),RRAM (resistive RAM), PCM (phase change memory), MAGRAM (magneticrandom-access memory), NAND flash, and one or more HDDs (hard diskdrives) when storage of the order of several terabytes is required. TheSLC non-volatile memory can be flash, PCM, RRAM, MAGRAM or any othersolid-state non-volatile memory as long as it has endurance that issuperior to that of MLC flash, and it provides for data access speedsthat are faster than that of MLC flash or rotating storage media (e.g.,HDDs).

BACKGROUND

Non-volatile memories provide long-term storage of data. Moreparticularly, non-volatile memories can retain the stored data even whennot powered. Magnetic (rotating) hard disk drives (HDD) dominate thisstorage medium due to lower cost compared to solid state disks (SSD).Optical (rotating) disks, tape drives and others have a smaller role inlong-term storage systems. SSDs are preferred for their superiorperformance (fast access time), mechanical reliability and ruggedness,and portability. Flash memory, more specifically NAND flash, is thedominant SSD medium today.

RRAM, PCM, MAGRAM and others, will likely play a larger role in thefuture, each of them having their own advantages and disadvantages. Theymay ultimately replace flash memories, initially for use as a “writebuffer” and later to replace “SLC flash” and “MLC flash.” MLC NAND flashis a flash memory technology using multiple levels per cell to allowmore bits to be stored using the same number of transistors. In SLC NANDflash technology, each cell can exist in one of two states, storing onebit of information per cell. Most MLC NAND flash memory has fourpossible states per cell, so it can store two bits of information percell.

These semiconductor technology driven “flash alternatives,” i.e., RRAM,PCM, MAGRAM and others, have several advantages over any (SLC or MLC)flash because they: 1) allow data to be written over existing data(without prior erase of existing data), 2) allow for an erase ofindividual bytes or pages (instead of having to erase an entire block),and 3) possess superior endurance (1,000,000 write-erase cycles comparedto typical 100,000 cycles for SLC flash and less than 10,000 cycles forMLC flash).

HDDs have several platters. Each platter contains 250-5,000 tracks(concentric circles). Each track contains 64 to 256 sectors. Each sectorcontains 512 bytes of data and has a unique “physical (memory) address.”A plurality of sectors is typically combined to form a “logical block”having a unique “logical address.” This logical address is the addressat which the logical block of physical sectors appears to reside fromthe perspective of an executing application program. The size of eachlogical block and its logical address (and/or address ranges/boundaries)is optimized for the particular operating system (OS) and softwareapplications executed by the host processor. A computer OS organizesdata as “files.” Each file may be located (stored) in either a singlelogical block or a plurality of logical blocks, and therefore, thelocation of files typically traverses the boundaries of individual(physical) sectors. Sometimes, a plurality of files has to be combinedand/or modified, which poses an enormous challenge for the memorycontroller device of a non-volatile memory system.

SSDs are slowly encroaching on the HDD space and the vast majority ofNAND flash in enterprise servers utilizes a SLC architecture, whichfurther comprises a NAND flash controller and a flash translation layer(FTL). NAND flash devices are generally fragmented into a number ofidentically sized blocks, each of which is further segmented into somenumber of pages. It should be noted that asymmetrical block sizes, aswell as page sizes, are also acceptable within a device or a modulecontaining devices. For example, a block may comprise 32 to 64 pages,each of which incorporates 2-4 Kbit of memory. In addition, the processof writing data to a NAND flash memory device is complicated by the factthat, during normal operation of, for example, single-level storage(SLC), erased bits (usually all bits in a block with the value of ‘1’)can only be changed to the opposite state (usually ‘0’) once before theentire block must be erased. Blocks can only be erased in theirentirety, and, when erased, are usually written to ‘1’ bits. However, ifan erased block is already there, and if the addresses (block, page,etc.) are allowed, data can be written immediately; if not, a block hasto be erased before it can be written to.

FTL is the driver that works in conjunction with an existing operatingsystem (or, in some embedded applications, as the operating system) tomake linear flash memory appear to the system like a disk drive, i.e.,it emulates a HDD. This is achieved by creating “virtual” small blocksof data, or sectors, out of flash's large erase blocks and managing dataon the flash so that it appears to be “write in place” when in fact itis being stored in different locations in the flash. FTL further managesthe flash so that there are clean/erased places to store data.

Given the limited number of writes that individual blocks within flashdevices can tolerate, wear leveling algorithms are used within the flashdevices (as firmware commonly known as FTL or managed by a controller)to attempt to ensure that “hot” blocks, i.e., blocks that are frequentlywritten, are not rendered unusable much faster than other blocks. Thistask is usually performed within a flash translation layer. In mostcases, the controller maintains a lookup table to translate the memoryarray physical block address (PBA) to the logical block address (LBA)used by the host system. The controller's wear-leveling algorithmdetermines which physical block to use each time data is programmed,eliminating the relevance of the physical location of data and enablingdata to be stored anywhere within the memory array and thus prolongingthe service life of the flash memory. Depending on the wear-levelingmethod used, the controller typically either writes to the availableerased block with the lowest erase count (dynamic wear leveling); or itselects an available target block with the lowest overall erase count,erases the block if necessary, writes new data to the block, and ensuresthat blocks of static data are moved when their block erase count isbelow a certain threshold (static wear leveling).

MLC NAND flash SSDs are slowly replacing and/or coexisting with SLC NANDflash in newer SSD systems. MLC allows a single cell to store multiplebits, and accordingly, to assume more than two values; i.e., ‘0’ or ‘1’.Most MLC NAND flash architectures allow up to four (4) values per cell;i.e., ‘00’, ‘01’, ‘10’, or ‘11’. Generally, MLC NAND flash enjoysgreater density than SLC NAND flash, at the cost of a decrease in accessspeed and lifetime (endurance). It should be noted, however, that evenSLC NAND flash has a considerably lower lifetime (endurance) thanrotating magnetic media (e.g., HDDs), being able to withstand onlybetween 50,000 and 100,000 writes, and MLC NAND flash has a much lowerlifetime (endurance) than SLC NAND flash, being able to withstand onlybetween 3,000 and 10,000 writes. As is well known in the art, any“write” or “program” to a block in NAND flash (floating gate) requiresan “erase” (of a block) before “write.”

Despite its limitations, there are a number of applications that lendthemselves to the use of MLC flash. Generally, MLC flash is used inapplications where data is read many times (but written few times) andphysical size is an issue. For example, flash memory cards for use indigital cameras would be a good application of MLC flash, as MLC canprovide higher density memory at lower cost than SLC memory.

When a non-volatile storage system combines HDD, SLC and MLC (settingaside volatile memory for buffering, caching etc) in a single (hybrid)system, new improvements and solutions are required to manage themethods of writing data optimally for improved life time (endurance) offlash memory. Accordingly, various embodiments of a NAND flash storagesystem that provides long lifetime (endurance) storage at low cost aredescribed herein.

The following description is presented to enable one of ordinary skillin the art to make and use the disclosure and is provided in the contextof a patent application and its requirements. Various modifications tothe preferred embodiment and the generic principles and featuresdescribed herein will be readily apparent to those skilled in the art.Thus, the present disclosure is not intended to be limited to theembodiments shown, but is to be accorded the widest scope consistentwith the principles and features described herein.

SUMMARY

According to one embodiment of the present disclosure, there is provideda system for storing data which comprises at least one MLC nonvolatilememory module (hereinafter referred to as “MLC module”) and at least oneSLC non-volatile memory module (hereinafter referred to as “SLCmodule”), each module comprises a plurality of individually erasableblocks. The data storage system according to one embodiment of thepresent disclosure further comprises a controller for controlling boththe at least one MLC module and the at least one SLC module. Inparticular, the controller maintains an address map comprising a list ofindividual logical address ranges each of which maps to a similar rangeof physical addresses within either the at least one MLC module or theat least one SLC module. After each write to (flash) memory, thecontroller conducts a data integrity check to ensure that the data waswritten correctly. When the data was not written correctly, thecontroller modifies the table so that the range of addresses on whichthe write failed is remapped to the next available range of physicaladdresses within the at least one SLC module. The SLC module can be(NAND) flash, PCM, RRAM, MAGRAM or any other solid-state non-volatilememory as long as it has endurance that is superior to that of MLCflash, and it provides for data access speeds that are faster than thatof MLC flash or rotating storage media (e.g., HDDs).

According to another embodiment of the present disclosure, there isprovided a system for storing data which comprises a controller that isfurther adapted to determine which of the blocks of the plurality of theblocks in the MLC and SLC non-volatile memory modules are accessed mostfrequently and wherein the controller segregates those blocks thatreceive frequent writes into the at least one SLC non-volatile memorymodule and those blocks that receive infrequent writes into the at leastone MLC nonvolatile module.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be more fully understood by reference to thefollowing detailed description of one or more preferred embodiments whenread in conjunction with the accompanying drawings, in which likereference characters refer to like parts throughout the views and inwhich:

FIG. 1 is a block diagram of a computer system incorporating oneembodiment of the present disclosure;

FIGS. 2A and 2B are drawings depicting a translation table/address mapin accordance with one embodiment of the present disclosure;

FIGS. 3A and 3B are a flow chart illustrating an exemplary method foruse in implementing one embodiment of the present disclosure; and

FIG. 4 is a block diagram depicting one embodiment of the presentdisclosure for implementation within a NAND flash module.

DETAILED DESCRIPTION

The present disclosure is directed to the reliable storage of data inread and write memory, and, in particular, to the reliable storage ofdata in non-volatile memory, such as, for example, NAND flash.Generally, and in particular regard to NAND flash memory, two separatebanks of NAND flash are maintained by a controller. One bank containseconomical MLC NAND flash, while a second bank contains high enduranceSLC NAND flash. The controller conducts a data integrity test afterevery write. If a particular address range fails a data integrity test,the address range is remapped from MLC NAND flash to SLC NAND flash. Asthe SLC NAND flash is used to boost the lifetime (endurance) of thestorage system, it can be considerably lesser in amount than the MLCNAND flash. For example, a system may set SLC NAND flash equal to 12.5%or 25% of MLC NAND flash (total non-volatile memory storagespace=MLC+SLC).

Turning to the Figures and to FIG. 1 in particular, a computer system 10depicting one embodiment of the present disclosure is shown. A processor12 is coupled to a device controller 14, such as a chipset, using a datalink well known in the art, such as a parallel bus or packet-based link.The device controller 14 provides interface functions to the processor12. In some computer systems, the device controller 14 may be anintegral part of the (host) processor 12. The device controller 14provides a number of input/output ports 16 and 18, such as, for example,serial ports (e.g., USB ports and Firewire ports) and network ports(e.g., Ethernet ports and 802.11 “Wi-Fi” ports). The device controller14 may also control a bank of, for example, DRAM 20. In addition, thedevice controller 14 controls access to one or more disks 24, such as,for example, a rotating magnetic disk, or an optical disk, as well astwo or more types of NAND flash memory. One type of NAND flash memory isa MLC NAND flash memory module 26. Another type of NAND flash memory isa SLC NAND flash memory module 28.

The device controller 14 maintains a translation table/address map whichmay include address translations for all devices in the computer system.Nonetheless, the discussion in the present disclosure will be limitedonly to NAND flash memory modules. In particular, the device controller14 maintains a translation table that maps logical computer systemaddresses to physical addresses in each one of the MLC- and SLC-NANDflash memory modules 26 and 28, respectively. As MLC flash memory isless expensive than SLC flash memory, on a cost per bit basis, thetranslation table will initially map all logical NAND flash addresses tothe MLC NAND flash memory module 26. The address ranges within thetranslation table will assume some minimum quantum, such as, forexample, one block, although a smaller size, such as one page could beused, if the NAND flash has the capability of erasing the smaller sizequantum.

A “read-modify-write” scheme is used to write data to the NAND flash.Data to be written to NAND flash is maintained in DRAM 20. After eachwrite to an address within a particular address range, the devicecontroller 14 will—as time permits—perform a read on the address rangeto ensure the integrity of the written data. If a data integrity testfails, the address range is remapped from the MLC NAND flash memorymodule 26 to the next available address range in the SLC NAND flashmemory module 28.

FIGS. 2A and 28 illustrate one embodiment of a translation table/addressmap of the present disclosure. In FIG. 2A, a list of logical addressranges (R0-RN) is translated to physical address ranges. As illustrated,all of the logical address ranges are translated to blocks on the MLCNAND flash memory module 26. However, through the application of a dataintegrity verification check (explained in more detail below) it isdetermined that, for example, address range R2 corresponds to failedquanta of data stored in block 2 of the MLC NAND flash memory module 26.FIG. 28 shows the quanta of data which failed the data integrityverification check (see FIG. 2A) remapped to the next available range ofphysical addresses within the SLC NAND flash memory module 28, in thisexample, SLC/block 0.

FIGS. 3A and 3B are a flow chart illustrating a method for utilizing aNAND flash memory system incorporating one embodiment of the presentdisclosure. The method begins in a step 100, when a command to write aquantum of data stored in DRAM to a particular location in NAND flashmemory is received. In step 102, the quantum of data is read from DRAMinto memory within the device controller (which acts as the memorycontroller). In step 104, both the logical address range and the NANDflash physical address range to which the quantum of data is to bewritten, is read into memory of the device controller. In step 106, thequantum of data to be written is combined with the contents of the NANDflash memory. In step 108, the NAND flash physical address range to bewritten is erased. In step 110, the combined data is written to theappropriate NAND flash physical address range. In step 112 the NANDflash physical address range that was written in step 110 is read intodevice controller memory.

The flowchart continues in FIG. 3B. In step 114 the NAND flash physicaladdress range that was read into device controller memory is comparedwith the retained data representing the combination of the previouscontents of the physical address range and the quantum of data to bewritten. In step 116, if the retained data matches the newly stored datain the NAND flash memory, the write was a success, and the method exitsin step 118. However, if the retained data does not match the newlystored data in the NAND flash memory, the method executes step 120,which identifies the next quantum of available SLC NAND flash memoryaddresses. In step 122, a check is made to determine if additional SLCNAND flash memory is available, and, if not, the NAND flash memorysystem is marked as failed, prompting a system alert step 124. However,if additional SLC NAND flash memory is available, the failed NAND flashphysical address range is remapped to the next available quantum of SLCNAND flash memory in step 126. Execution then returns to step 110, wherethe write is repeated.

Another application of one embodiment of the present disclosure, notdepicted in any of the drawings, is to allocate “hot” blocks; i.e.,those blocks that receive frequent writes, into the SLC NAND flashmemory module 28, while allocating “cold” blocks; i.e., those blocksthat only receive infrequent writes, into the MLC NAND flash memorymodule 26. This could be accomplished within the device controller 14described above, which could simply maintain a count of those blocksthat are accessed (written to) most frequently, and, on a periodicbasis, such as, for example, every 1000 writes, or every 10,000 writes,transfer the contents of those blocks into the SLC NAND flash memorymodule 28.

FIG. 4 depicts another embodiment of the present disclosure. Theembodiment is entirely resident within a NAND flash module 50. Inparticular, a standard NAND flash interface 52 is managed by flashtranslation layer (FTL) logic 54. The flash translation layer (FTL) 54manages two NAND flash memory banks 56 and 58, whereby memory bank 56comprises a plurality of MLC NAND flash memory modules 60 a and aplurality of SLC NAND flash memory modules 62 a. Memory bank 58comprises a plurality of MLC NAND flash memory modules 60 b and aplurality of SLC NAND flash memory modules 62 b.

This embodiment of the present disclosure could function similarly tothe system level embodiment discussed earlier with reference to FIGS.1-3B, but the control functions, such as maintenance of the translationtable/address map (FIGS. 2A and 2B), could be conducted within the flashtranslation layer (FTL) 54 instead of in a device controller 14.

Embodiments of the present disclosure relate to a system and method ofincreasing the reliability and lifetime of a NAND flash storage system,module, or chip through the use of a combination of multi-level cell(MLC) and single-level cell (SLC) NAND flash storage. The abovedescription is presented to enable one of ordinary skill in the art tomake and use the disclosure and is provided in the context of a patentapplication and its requirements. While this disclosure containsdescriptions with reference to certain illustrative aspects, it will beunderstood that these descriptions shall not be construed in a limitingsense. Rather, various changes and modifications can be made to theillustrative embodiments without departing from the true spirit, centralcharacteristics and scope of the disclosure, including thosecombinations of features that are individually disclosed or claimedherein. Furthermore, it will be appreciated that any such changes andmodifications will be recognized by those skilled in the art as anequivalent to one or more elements of the following claims, and shall becovered by such claims to the fullest extent permitted by law.

What is claimed is:
 1. A system for storing data comprising: memoryspace containing volatile memory space and nonvolatile memory space,wherein the nonvolatile memory space includes both multi-level cell(MLC) space and single level cell (SLC) space; at least one controllerto operate memory elements and associated memory space for associatedWrite access operations to the memory elements and Read accessoperations from the memory elements; a bank of nonvolatile memory,including: a plurality of MLC memory modules, each including at leastone MLC nonvolatile memory element, and at least one SLC memory moduleincluding at least one SLC nonvolatile memory element; at least onerandom access volatile memory element; a flash translation layer (FTL),wherein the at least one controller, or the FTL, or a combination ofboth maintain an address table in one or more of the memory elements;the controller having associated controller memory for storing receiveddata therein, the controller controlling access of the MLC and SLCnonvolatile memory elements and the random access volatile memoryelements for storage of the received data therein as stored data, thecontroller, in at least a Write access operation transferring the storedreceived data from the controller memory to a given one of the MLCnonvolatile memory elements in an associated MLC memory module, operableto store the received data in the given one of the MLC nonvolatilememory elements as stored data and retain such received data in therandom access volatile memory as retained data associated with storeddata; the controller performing a data integrity test on stored data inthe given one of the MLC nonvolatile memory elements in the associatedone of the MLC memory modules after the at least a Write accessoperation performed thereon by reading the stored data to the controllermemory and comparing the stored data in the controller memory in thegiven one of the MLC nonvolatile memory elements to the retained datathat was associated with the stored data in the random access volatilememory by the controller during the Write access operation; wherein theaddress table maps logical and physical addresses adaptable to thesystem, wherein the mapping is performed as necessitated by the systemto maximize lifetime, and wherein the mapping maps blocks, pages, orbytes of data in either volatile or nonvolatile, or both, memories; andwherein a failure of the data integrity test performed on the storeddata by the controller results in a remapping of address space to adifferent physical range of addresses and transfer of data correspondingto the retained data to those remapped physical addresses from thosephysical addresses determined to have failed the data integrity test. 2.The system of claim 1, wherein the FTL is a software module, or afirmware module containing software updates.
 3. The system of claim 1,wherein at least one of the random access volatile memory or the MLC andSLC nonvolatile memory elements are embedded in the at least onecontroller.
 4. The system of claim 1, wherein the MLC and SLCnonvolatile memory elements comprise flash memory.
 5. The system ofclaim 1, wherein the random access volatile memory element is dynamicrandom access memory.
 6. The system of claim 1, wherein the randomaccess volatile memory element is static random access memory.
 7. Thesystem of claim 1, wherein the at least one SLC nonvolatile memoryelement includes a hard disk drive (HDD).